I think you might need to consider initialization order a little bit more. when does the index actually get set? Is it before or after the nickname gets initialized?

This would mean that the 5th pipeline made would have the 5 suffix appended to it if no name was specified which isn't the desired behavior. Logic needs to be implemented here to check the occurrence count of a current name and increment that. Pipeline names are already gauntleted to be unique when creating a new pipeline by the UI so you just need to handle the duplicating case.

This would mean that the 5th pipeline made would have the 5 suffix appended to it if no name was specified which isn't the desired behavior. Logic needs to be implemented here to check the occurrence count of a current name and increment that. Pipeline names are already gauntleted to be unique when creating a new pipeline by the UI so you just need to handle the duplicating case.

I think I have an idea, is there a method that I can use to get all of the pipeline indices that are currently being used? This way I can check to see which numbers are being used, find the max number from there, and add one to it as the new pipeline index assuming the current index isn't the integer max value.

I took a look at the code and drew a full diagram out, it seems to work fine. It leaves me wondering what the original issue was, then.